This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
There is indeed a significant learning curve in setting up a reverse proxy. There are instructions out there, but many of them lack bits and pieces, like fixing the REMOTE_ADDR environment variable and breaking web log statistics. Still, it is an alternative that I felt should be put out there. I set up a reverse proxy after POODLE, before IBM released their fix. As a result, I was barely affected by the POODLE TLS vulnerability.
Don't actually know how a reverse proxy relates to anti-spam. I believe mail relays and reverse proxies are different.
Edit: It occurred to me that you might have been talking about comment or forum spam. If this broke because of the REMOTE_ADDR being wrong, there is a way to fix that. Specifically, you can enable processing of the Websphere connector headers described at http://www.kalechi.com/doc/notesini.nsf/0/6f6d43f04f1bcf2bc1256e9e004423ff . This allows you to pass special headers from the reverse proxy to Domino, overriding things like the Remote Address, Remote Host, and HTTPS status.
Feedback response number WEBB9SRPKH created by ~Carol Asafreekonyli on 01/14/2015
You are right
Return to top
. . . . . . . . . . . . . . . . . . You are right (~Carol Asafreek... 14.Jan.15) 
